Important: Unless otherwise specified, all information in this chapter applies to both Sun Solaris- and Red Hat Enterprise Linux-based WEM systems.
Important: If you are uninstalling WEM in any clustered setup prior to an upgrade, the node has to be put into maintenance mode first (i.e. removed from the resource group). This ensures that all the processes running on this node are stopped and prevents the active node from failing over to become the standby node. For more information on this procedure, please refer to WEM High Availability Redundancy with Cluster Application in the appendices. |
•
|
All data files, typically located in the /<ems_dir>/server/data directory and all subdirectories residing there (i.e. /bulkstats, etc.).
|
|
•
|
PostgreSQL data files, located in the ~postgres/data or users/postgresx.x.x/data directory. Refer to the Backing-up WEM Databases section of the WEM Database Maintenance chapter in this guide for more information.
|
Important: Downgrading the WEM application to an earlier version is not supported at this time. You must uninstall the current version and install the older version using the instructions located in Installing the WEM Software chapter of this guide. Please contact your local sales representative for information on preserving data stored by the current WEM instance prior to uninstalling.|
•
|
GUI-based method: This method is the most often used uninstallation procedure. Requirements for using this method include:
|
Important: If the uninstall GUI does not open, add X-windows port (TCP/6000) in the exception list of Windows firewall.|
•
|
Console-based method: This method is available to users who do not have an X-Windows client available for remote network connectivity to the WEM server via Telnet or SSH.
|
Important: The GUI-based uninstall script is designed to protect all the historical data files that are currently in use. However, it is still recommended that you manually perform a backup of these files before continuing.|
Step 1
|
|
Step 2
|
Go to the directory in which WEM is installed (the /users/ems directory by default) by entering the following command:
|
|
Step 3
|
Go to the /_uninst sub-directory by entering the following command:
|
|
Step 5
|
Click the Next button. A dialog appears identifying the processes to be stopped.
|
|
Step 6
|
Click Next and follow the on-screen instructions.
|
|
Step 7
|
Click Finish to complete the uninstallation process.
|
The uninstall script leaves the /ems directory in place with several sub-directories.
|
Step 8
|
Optional: If all critical and historical data files have been properly backed up, delete the /ems directory using the following commands:
|
Important: If you decided to keep the /ems directory, it is highly recommended that at the very least you delete the _uninst directory. Failure to remove this directory before installing a new version of the WEM application using the GUI-based installation method will result in a different _uninst directory being created each time you perform a software upgrade. This results in the creation of multiple uninstall directories (i.e. named /_uninst2, /_uninst3, etc.). The uninst file needed for the next uninstall would have to be located there.
Important: The console-based uninstall script is designed to protect all the historical data files that are currently in use. However, it is still recommended that you manually perform a backup of these files before proceeding with this procedure.|
Step 1
|
|
Step 2
|
Go to the directory in which WEM is installed (the /users/ems directory by default) by entering the following command:
|
|
Step 3
|
Go to the /_uninst sub-directory by entering the following command:
|
Upon completion, the uninstall script indicates that certain sub-directories were not deleted within the /ems directory.
|
Step 8
|
Optional: If all critical and historical data files have been properly backed up, delete the /ems directory using the following commands:
|
Important: If you decide to keep the /ems directory, it is highly recommended that at the very least you delete the _uninst directory. Failure to remove this directory before installing a new version of the WEM application using the GUI-based installation method will result in a different _uninst directory being created each time you perform a software upgrade. This results in the creation of multiple uninstall directories (i.e. named /_uninst2, /_uninst3, etc.). The uninst file needed for the next uninstall would have to be located there.